When to update the version of the runtime system on the PLC?

This is how you are able to quickly check in Neuron Power Engineer whether a more current version of the PLC runtime system is recommended for usage with the application:

In the Instance view: Select the requested PLC (= appertaining IEC-resource with icon ) or one of the children.
Result: Above the toolbar for the view, the selected PLC incl. the project name is displayed.
Connect to the PLC.
Expand the item PLC Information for the IEC-resource. Then expand the item Runtime system.
Make sure that the items for Current version and Recommended version quote an identical version.
In case of different versions, the correct execution of the application on the PLC or even the successful loading of the application cannot be granted. Best practice in this case: Install the recommended version of the runtime system on the PLC.

Good to know

Good to know
It is not possible to use a runtime system version < 4.0.0 with the Neuron Power Engineer version 2.0.0 or a following version. Reason: So far, the code has been generated with 2 different data structures for resolving the names of variables (for the Values of Variables view). The new data structure supports enhanced features, such as the representation of values for →reference variables within the Values of Variables view. The old data structure has been kept for incl. the Neuron Power Engineer version 1.126.0 in order to maintain the compatibility of previous runtime system versions with these Neuron Power Engineer versions. When using the Neuron Power Engineer version 2.0.0 or a later version, observe that the redundant data is no longer generated. If you are using a runtime system < 4.0.0 version and you want to use the current Neuron Power Engineer version, upgrade to the current runtime system version. The current installation package for runtime system is included in the delivery range of Neuron Power Engineer. It is not possible to use a runtime systemversion < 5.0.0 with the Neuron Power Engineer version 3.1.0 or a following version. Reason: Neuron Power Engineer version 3.1.0 generates nameserver code that cannot be processed by a runtime system version < 5.0.0 Neuron Power Engineer checks the version of the runtime system when the application is loaded. If Neuron Power Engineer requires a more current runtime system version, the following message is displayed: `Version of runtime system is a.b.c but must be x.y.z. The application for the PLC (resource "name", platform toolkit "name") cannot be created/loaded.` If you do not need this check, contact your administrator or system integrator and ask for the deactivation of this check. It is not possible to use a runtime system version < 5.1.0 with the Neuron Power Engineer version 3.6.0, if you want to build/load an application using →interfaces incl.→method prototypes. Moreover, some system blocks (such as the SaveRetainData block or the LoadRetainData block) do not work as excepted within the built/loaded application, if you are using a runtime system version ≤ 5.0.0 with Neuron Power Engineer version ≥ 3.6.0. Reason: Neuron Power Engineer version 3.6.0 generates nameserver code that cannot be processed correctly by runtime system version 5.0.0. In contrast to this: It is possible to use the runtime system version 5.0.0 again with the Neuron Power Engineer version 3.7.0 or a following version – even if you are using interfaces incl. method prototypes or the mentioned blocks in the built/loaded application.

(grey lightbulb) It is not possible to use a runtime system version < 4.0.0 with the Neuron Power Engineer version 2.0.0 or a following version.
Reason: So far, the code has been generated with 2 different data structures for resolving the names of variables (for the Values of Variables view).

The new data structure supports enhanced features, such as the representation of values for →reference variables within the Values of Variables view.

The old data structure has been kept for incl. the Neuron Power Engineer version 1.126.0 in order to maintain the compatibility of previous runtime system versions with these Neuron Power Engineer versions.

When using the Neuron Power Engineer version 2.0.0 or a later version, observe that the redundant data is no longer generated. If you are using a runtime system < 4.0.0 version and you want to use the current Neuron Power Engineer version, upgrade to the current runtime system version. The current installation package for runtime system is included in the delivery range of Neuron Power Engineer.

(grey lightbulb) It is not possible to use a runtime systemversion < 5.0.0 with the Neuron Power Engineer version 3.1.0 or a following version.
Reason: Neuron Power Engineer version 3.1.0 generates nameserver code that cannot be processed by a runtime system version < 5.0.0

Neuron Power Engineer checks the version of the runtime system when the application is loaded. If Neuron Power Engineer requires a more current runtime system version, the following message is displayed:
Version of runtime system is a.b.c but must be x.y.z. The application for the PLC (resource "name", platform toolkit "name") cannot be created/loaded.

If you do not need this check, contact your administrator or system integrator and ask for the deactivation of this check.

(grey lightbulb) It is not possible to use a runtime system version < 5.1.0 with the Neuron Power Engineer version 3.6.0, if you want to build/load an application using →interfaces incl.→method prototypes.
Moreover, some system blocks (such as the SaveRetainData block or the LoadRetainData block) do not work as excepted within the built/loaded application, if you are using a runtime system version ≤ 5.0.0 with Neuron Power Engineer version ≥ 3.6.0.
Reason: Neuron Power Engineer version 3.6.0 generates nameserver code that cannot be processed correctly by runtime system version 5.0.0.

In contrast to this: It is possible to use the runtime system version 5.0.0 again with the Neuron Power Engineer version 3.7.0 or a following version – even if you are using interfaces incl. method prototypes or the mentioned blocks in the built/loaded application.